method of performing a procedure related to amf registration by udm in a wireless communication syst

专利摘要:
in one embodiment of the present invention, a method for allowing an udm (unified data management) to perform a procedure related to registering an amf (mobility and access management function) in a wireless communication system comprises the steps of: receive, through the udm, a message related to an eu server's amf registration, which includes access type information and id (identity) information from a first amf; transmit, through the udm, a message related to the cancellation of registration to a second amf when there is the second amf, in which the second amf is registered as an eu server amf and related to the type of access information.
公开号:BR112019021178A2
申请号:R112019021178
申请日:2018-04-26
公开日:2020-04-28
发明作者:Kim Hyunsook；Ryu Jinsook；Kim Laeyoung；Youn Myungjune；Park Sangmin
申请人:Lg Electronics Inc；
IPC主号:

专利说明:

"METHOD OF EXECUTION OF PROCEDURE RELATING TO AMF REGISTRATION BY UDM IN WIRELESS COMMUNICATION SYSTEM, AND DEVICE FOR THE SAME."
TECHNICAL FIELD [001] The following description refers to a wireless communication system and, more particularly, to a method for allowing the UDM (Unified Data Management) to perform a procedure related to the registration of AMF (Function of Access and Mobility Management) and a device for it.
BACKGROUND OF THE TECHNIQUE [002] Wireless communication systems have been widely installed to provide various types of communication services such as voice or data. In general, a wireless communication system is a multiple access system that supports the communication of several users, sharing the available system resources (bandwidth, transmission power, etc.) between them. For example, multiple multiple access systems include a Code Division Multiple Access system (CDMA), a Frequency Division Multiple Access system (FDMA), a Time Division Multiple Access system (TDMA), a system Orthogonal Frequency Division Multiple Access (OFDMA), a Single Carrier Frequency Division Multiple Access (SC-FDMA), and a Multiple Carrier Frequency Division Multiple Access (MC-FDMA) system.
REVELATION
TECHNICAL PROBLEM [003] An objective of the present invention is to provide a method to allow a UDM to efficiently perform AMF registration on a 5G mobile communication system.
[004] It will be understood by those skilled in the art that the objectives
Petition 870190101048, of 10/09/2019, p. 16/97
2/53 could be achieved with the present invention are not limited to what was particularly described above and that the above objectives and others that the present invention could achieve will be more clearly understood from the detailed description below.
TECHNICAL SOLUTIONS [005] In one embodiment of the present invention, a method for allowing a UDM (Unified Data Management) to perform a procedure related to the registration of an AMF (Access and Mobility Management Function) in a wireless communication system The wire comprises the steps of: receiving, through the UDM, a message related to the AMF record serving a UE, which includes access type information and ID (Identity) information from a first AMF; transmit, through the UDM, a message related to deregistration to a second AMF when there is a second AMF, in which the second AMF is registered as an AMF serving the UE and related to the type of access information.
[006] In an embodiment of the present invention, a UDM (Unified Data Management) device to perform a procedure related to the registration of an AMF (Access and Mobility Management Function) in a wireless communication system comprises a transceiver; and a processor, where the processor allows the UDM to receive a message related to the UE's AMF record, which includes access type information and ID (Identity) information, from a first AMF, and if any a second AMF registered as an UE serving AMF, which corresponds to the type of access information, the UDM transmits a message related to deregistration to the second AMF.
[007] G UDM can store access type information related to MFA and ID information.
Petition 870190101048, of 10/09/2019, p. 17/97
3/53 [008] The UDM can receive a request message related to the deletion of UE context from NF, and the request message related to deletion of UE context can include information of the type of access when the NF is AM F .
[009] The UDM transmitted the message related to deregistration due to the withdrawn subscription, this may indicate a type of message access related to deregistration.
[010] If a message to request AMF server information is received from the NF, the server AMF information related to the access type can be transmitted to the NF, and the server AMF information request message can include information of the access type .
[011] The method may further comprise the step of receiving a request to request NF UE reachability information, where the request to request reachability information from the UE may include information on the type of access.
[012] The UDM can be subscribed to a notification service for EU reachability event by the MFA related to the type of access.
[013] If information indicating that the UE is accessible is received from the MFA related to the type of access, information indicating that the UE is accessible can be transmitted to the NF.
[014] If the UE performs the handover from a 5GS (5G system) to an EPS (Evolved Packet System), the cancellation location by the UDM and the HSS can be performed for AMF whose access type is 3GPP.
[015] If the UE exchanges a 5GS for an EPS in an idle mode, a UDM cancel location operation can be performed for AMF whose access type is 3GPP.
ADVANTAGE EFFECTS
Petition 870190101048, of 10/09/2019, p. 18/97
4/53 [016] According to the present invention, an AMF server and / or related information can be efficiently managed in a state that the AMF can exist by access by virtue of 3GPP and non-3GPP access.
[017] It will be understood by those skilled in the art that the effects that could be obtained with the present invention are not limited to what was particularly described above and that other advantages of the present invention will be more clearly understood from the detailed description below.
BRIEF DESCRIPTION OF THE DRAWINGS [018] The accompanying drawings, which are included to provide a further understanding of the invention, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.
[019] Figure 1 is a diagram that illustrates a brief structure of an evolved package system (EPS) that includes an evolved package core (EPC).
[020] Figure 2 is an example diagram that illustrates an architecture of a general E-UTRAN and a general EPC.
[021] Figure 3 is an example diagram that illustrates a structure of a radio interface protocol in a control plane.
[022] Figure 4 is an example diagram that illustrates a structure of a radio interface protocol in a user plane.
[023] Figure 5 is a flow chart illustrating a random access procedure.
[024] Figure 6 is a diagram illustrating a connection procedure in a radio resource control (RRC) layer.
[025] Figure 7 is a diagram illustrating the 5G system.
[026] Figure 8 illustrates a NextGe Architecture without Roaming.
[027] Figures 9 to 21 are diagrams that illustrate examples of a detailed procedure according to the modalities of the present invention.
Petition 870190101048, of 10/09/2019, p. 19/97
5/53 [028] Figure 22 is a diagram illustrating a configuration of a knot device according to the embodiment of the present invention.
BEST MODE FOR CARRYING OUT THE INVENTION [029] The modalities below are combinations of components and features of the present invention in a prescribed form. Each component or feature can be considered as selective, except where explicitly stated otherwise. Each component or characteristic can be executed in a way that is not combined with other components and features. In addition, some components and / or resources can be combined to configure a modality of the present invention. The order of operations described in the modalities of the present invention can be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced by a corresponding component or feature of the present invention.
[030] The specific terms used in the description below are provided to assist the understanding of the present invention, and the use of such specific terms may be changed to another form within the scope of the technical concept of the present invention.
[031] In some cases, to avoid obscurity of the concept of the present invention, a known structure and apparatus may be omitted or a block diagram centered on the main functions of each structure or apparatus may be used. In addition, similar numerical references are used for similar components throughout the specification.
[032] The modalities of the present invention can be supported by standard documents disclosed in relation to at least one among the IEEE (Institute of Electrical and Electronic Engineers) group 802, 3GPP system, 3GPP LTE & LTE-A system and 3GPP2 system. That is, the steps or parts that have not been described to clarify the technical concept of the present invention in
Petition 870190101048, of 10/09/2019, p. 20/97
6/53 embodiments of the present invention can be supported by the above documents. In addition, all terms disclosed in this document can be described in accordance with the standard documents above.
[033] The technology below can be used for various wireless communication systems. For clarity, the description below focuses on 3GPP LTE and 3GPP LTE-A, where the technical idea of the present invention is not limited.
[034] The terms used in this document are defined as follows.
[035] - IIMTS (Universal Mobile Telecommunications System): a third generation mobile communication technology based on GSM (Global Mobile Communications System) developed by 3GPP.
[036] - EPS (Evolved Packet System): a network system that includes an EPC (Evolved Packet Core), which is a packet-switched core network based on IP (Internet Protocol) and an access network such as LTE and UTRAN. This system is the network of an evolved version of UMTS.
[037] - NodeB: a GERAN / UTRAN base station. This base station is installed externally and its cover has a macro cell scale.
[038] - eNodeB: an LTE base station. This base station is installed externally and its cover has a macro cell scale.
[039] - UE (User Equipment): the UE can be called a terminal, ME (Mobile Equipment), MS (Mobile Station) etc. In addition, the UE can be a portable device, such as a notebook, a cell phone, a PDA (Personal Digital Assistant), a smartphone and a multimedia device. Alternatively, the UE can be a non-portable device such as a PC (Personal Computer) and a vehicle-mounted device. The term "UE", as used in connection with MTC, can refer to an MTC device.
Petition 870190101048, of 10/09/2019, p. 21/97
7/53 [040] - HNB (Domestic NodeB): a base station of UMTS network. This base station is installed internally and its cover has a micro cell scale.
[041] - HeNB (Domestic eNodeB): a base station of an EPS network. This base station is installed internally and its cover has a micro cell scale.
[042] - MME (Mobility Management Entity): a network node of an EPS network, which performs mobility management (MM) and session management (SM).
[043] - PDN-GW (Packet Data Network Gateway) / PGW: a network node of an EPS network, which performs UE IP address allocation, packet sorting and filtering, loading data collection, etc.
[044] - SGW (Service Gateway): a network node of an EPS network, which performs the mobility anchor, packet routing, idle packet buffering, and triggering an MME UE paging.
[045] - NAS (Non-Access Stratum): a superior stratum of a control plan between an UE and an MME. This is a functional layer for transmitting and receiving a signaling and traffic message between an UE and a core network in an LTE / UMTS protocol stack and supports the mobility of an UE and supports a session management procedure to establish and maintain the IP connection between a UE and a GW PDN.
[046] - Packet Data Network (PDN): a network on which a server that supports a specific service (for example, a Multimedia Messaging Service (MMS) server, a Wireless Application Protocol server ( WAP), etc.) is located.
[047] - PDN connection: a logical connection between a UE and a PDN, represented as an IP address (an IPv4 address and / or an IPv6 prefix).
Petition 870190101048, of 10/09/2019, p. 22/97
8/53 [048] - RAN (Radio Access Network): a unit that includes a Node B, an eNode B, and a Radio Network Controller (RNC) to control Node B and eNode B on a network 3GPP, which is present between UEs and provides a connection to a core network.
[049] - HLR (Local Location Registry) / HSS (Local Subscriber Server): a database that has subscriber information on a 3GPP network. The HSS can perform functions such as configuration storage, identity management and user state storage.
[050] - PLMN (Public Terrestrial Mobile Network): a network configured for the purpose of providing mobile communication services to individuals. This network can be configured by operator.
[051] - Proximity Services (or ProSe Service or Proximity-based Service): a service that allows discovery between physically close devices, and direct mutual communication / communication through a base station / communication through third parties. At that time, user plan data is exchanged via a direct data path without a 3GPP core network (for example, EPC).
EPC (Evolved Packet Core) [052] Figure 1 is a schematic diagram showing the structure of an evolved packet system (EPS) that includes an evolved packet core (EPC).
[053] EPC is a core element of system architecture evolution (SAE) to improve the performance of 3GPP technology. SAE corresponds to a research project to determine a network structure that supports mobility between various types of networks. For example, SAE aims to provide a package-based system optimized to support various radio access technologies and to provide enhanced data transmission capabilities.
[054] Specifically, the EPC is a core network of an
Petition 870190101048, of 10/09/2019, p. 23/97
9/53 IP mobile communication for LTE 3GPP and can support packet-based services in real time and not real time. In conventional mobile communication systems (ie second or third generation mobile communication systems), the functions of a core network are implemented through a circuit-switched subdomain (CS) for voice and a packet-switched subdomain (PS ) for data. However, in an LTE 3GPP system that is developed from the third generation communication system, the CS and PS subdomains are unified in an IP domain. That is, in LTE3 GPP, the connection of terminals with IP capability can be established through an IP-based business station (for example, an eNodeB (evolved B node)), EPC and an application domain (for example, IMS ). That is, EPC is an essential framework for end-to-end IP services.
[055] The EPC can include several components. Figure 1 shows some components, that is, a server gateway (SGW), a packet data network gateway (PDN GW), a mobility management entity (MME), a support node (SGSN) of a GPRS server (general packet radio service) and an advanced packet data gateway (ePDG).
[056] SGW operates as a boundary point between a radio access network (RAN) and a core network and maintains a data path between an eNodeB and the PDN GW. When the terminal moves over an area served by an eNodeB, the SGW functions as a local mobility anchor point. In other words, the packets can be routed through the SGW for mobility in an access network via an advanced UMTS terrestrial radio (E-UTRAN) defined after 3GPP version-8. In addition, SGW can serve as an anchor point for the mobility of another 3GPP network (an RAN defined before 3GPP version-8, for example, UTRAN or GERAN (global mobile communication system (GSM)) / enhanced data rates for the global evolution radio access network (EDGE)).
Petition 870190101048, of 10/09/2019, p. 24/97
10/53 [057] The GW PDN corresponds to a data interface endpoint for a packet data network. The GW PDN can support policy enforcement, packet filtering and billing support features. In addition, the GW PDN can serve as an anchor point for mobility management with a 3GPP network and a non-3GPP network (for example, an untrusted network such as an interoperable wireless local area network (l-WLAN) and a network reliable as code division multiple access (CDMA) or WiMax network).
[058] Although the SGW and PDN GW are configured as separate gateways in the network structure example in Figure 1, the two gateways can be implemented according to a single gateway configuration option.
[059] MME performs signaling and control functions to support the access of a UE for network connection, allocation of network resources, tracking, paging, roaming and handover. MME controls control plan functions associated with subscriber and session management. MME manages several eNodeBs and signals the selection of a conventional gateway for handover to other 2G / 3G networks. In addition, MME performs security procedures, terminal-to-network session manipulation, and inactive terminal location management, etc.
[060] SGSN handles all packet data like managing mobility and authenticating a user to other 3GPP networks (for example, a GPRS network).
[061] ePDG serves as a security node for a non-3GPP network (for example, an l-WLAN, a Wi-Fi hotspot, etc.).
[062] As described above with reference to Figure 1, a terminal that has IP capabilities can access an IP service network (for example, an IMS) provided by an operator through various elements in the EPC not only based on 3GPP access but also also based on non-3GPP access.
Petition 870190101048, of 10/09/2019, p. 25/97
11/53 [063] In addition, Figure 1 shows several reference points (for example, S1-U, S1-MME, etc.). In 3GPP, a conceptual link that connects two functions of different functional entities of an E-UTRAN and an EPC is defined as a reference point. Table 1 is a list of the landmarks shown in Figure 1. Several landmarks may be present in addition to the landmarks in Table 1 according to network structures.
[TABLE 1]
Reference point description S1-MME Reference point for the control plan protocol between E-UTRAN and MME S1-U Reference point between E-UTRAN and Service GW for tunneling the user plane by carrier and switching the inter eNodeB path during the handover S3 It allows the exchange of user and carrier information for the mobility of the inter 3GPP access network in the inactive and / or active state. This reference point can be used intra-PLMN or inter-PLMN (for example, in the case of HO Inter-PLMN). S4 It provides control support and related mobility between the GPRS Core and the 3GPP Anchor Service GW function. In addition, if the Direct Tunnel is not established, it provides tunneling of the user's plane. S5 It provides user plan tunneling and tunnel management between the Service GW and the GW PDN. It is used for relocation of Service GW due to UE mobility and if the S-GW needs to connect to a non-placed GW PDN for the required PDN connectivity S11 Reference point between an MME and an SGW SGi It is the reference point between the PDN GW and the packet data network. The packet data network can be a public or private packet data network or an intraoperator packet data network, for example, for the provision of IMS services. This reference point corresponds to Gi for 3GPP accesses.
[064] Among the reference points shown in Figure 1, S2a and S2b correspond to non-3GPP interfaces. S2a is a reference point that provides reliable non-3GPP access and related control and mobility support between PDN GWs to a user plan. S2b is a reference point that provides control and mobility support related between the ePDG and PDN GW to the user plan.
Petition 870190101048, of 10/09/2019, p. 26/97
12/53 [065] Figure 2 is a diagram that illustrates in an exemplary way the architectures of a typical E-UTRAN and EPC.
[066] As shown in the figure, as long as the radio resource control (RRC) connection is enabled, an eNodeB can perform routing to a gateway, broadcasting a paging message, programming and broadcasting a broadcast channel (BCH), dynamic allocation of resources to an UE in an upward and downward link, configuration and provision of eNodeB measurement, radio carrier control, radio admission control and connection mobility control. In EPC, paging generation, LTEJDLE state management, user plan encryption, SAE carrier control, and NAS signaling integrity protection and encryption.
[067] Figure 3 is a diagram that illustrates in an exemplary way the structure of a radio interface protocol in a control plane between a UE and a base station, and Figure 4 is a diagram that illustrates in an exemplary way structure of a radio interface protocol in a user plane between the UE and the base station.
[068] The radio interface protocol is based on the 3GPP wireless access network standard. The radio interface protocol horizontally includes a physical layer, a data link layer and a network layer. The radio interface protocol is divided into a user plane for transmitting data information and a control plane to provide control signals that are arranged vertically.
[069] Protocol layers can be classified into a first layer (L1), a second layer (L2) and a third layer (L3) based on the three sublayers of the open system interconnection model (OSI) which is well known in the communication system.
[070] Later in this document, a description of a
Petition 870190101048, of 10/09/2019, p. 27/97
13/53 radio protocol in the control plane shown in Figure 3 and a radio protocol in the user plane shown in Figure 4.
[071] The physical layer, which is the first layer, provides an information transfer service using a physical channel. The physical layer is connected to a medium access control layer (MAC), which is an upper layer of the physical layer, through a transport channel. Data is transferred between the physical layer and the MAC layer through the transport channel. The transfer of data between different physical layers, that is, a physical layer of a transmitter and a physical layer of a receiver is carried out through the physical channel.
[072] The physical channel consists of a plurality of subframes in the time domain and a plurality of subcarriers in the frequency domain. A subframe consists of a plurality of symbols in the time domain and a plurality of subcarriers. A subframe consists of a plurality of resource blocks. A resource block consists of a plurality of symbols and a plurality of subcarriers. A Transmission Time Interval (TTI), a unit of time for data transmission, is 1 ms, which corresponds to a subframe.
[073] According to 3GPP LTE, the physical channels present in the physical layers of the transmitter and receiver can be divided into data channels corresponding to the Physical Downlink Shared Physical Channel (PDSCH) and Uplink Shared Physical Channel (PUSCH) ) and control channels corresponding to the Physical Downlink Control Channel (PDCCH), Physical Control Format Indicator Channel (PCFICH), Hybrid ARQ Indicator Physical Channel (PHICH) and Physical Uplink Control Channel (PUCCH).
[074] The second layer includes several layers.
Petition 870190101048, of 10/09/2019, p. 28/97
14/53 [075] First, the MAC layer in the second layer serves to map several logical channels to several transport channels and also serves to map several logical channels to a transport channel. The MAC layer is connected to an RLC layer, which is an upper layer, through a logical channel. The logical channel is largely divided into a control channel for transmitting information from the control plane and a traffic channel for transmitting information from the user plane according to the types of information transmitted.
[076] The radio link control (RLC) layer in the second layer serves to segment and concatenate data received from an upper layer to adjust the size of the data so that the size is suitable for a lower layer to transmit the data in one radio interval.
[077] The PDCP (Packet Data Convergence Protocol) layer in the second layer performs a header compression function to reduce the size of an IP packet header that is relatively large in size and contains unnecessary control information to transmit with efficiency an IP packet as an IPv4 or IPv6 Packet over a radio range that has a narrow bandwidth. In addition, in LTE, the PDCP layer also performs a security function, which consists of encryption to prevent third parties from monitoring data and integrity protection to prevent data manipulation by third parties.
[078] The Radio Resource Control (RRC) layer, which is located at the top of the third layer, is defined only in the control plane and serves to configure radio carriers (RBs) and control a logical channel, a transport channel and a physical channel in relation to the reconfiguration and release operations. The RB represents a service provided for the second layer in order to guarantee the transfer of data between a UE and the E-UTRAN.
Petition 870190101048, of 10/09/2019, p. 29/97
15/53 [079] If an RRC connection is established between the RRC layer of the UE and the RRC layer of an E-UTRAN, the UE is in the RRC Connected mode. Otherwise, the UE is in the RRC idle mode.
[080] Later in this document, the description of the RRC status of the UE and a method of connecting RRC will be given. The RRC status refers to a state in which the UE RRC is or is not logically connected to the E-UTRAN RRC. The RRC state of the UE that has a logical connection to the RRC of the E-UTRAN is called an RRC_CONNECTED state. The RRC state of the UE that has no logical connection to the RRC of the E-UTRAN is called an RRCJDLE state. A UE in the RRC_CONNECTED state has an RRC connection, so the E-UTRAN can recognize the presence of the UE in a cell unit. Consequently, the UE can be efficiently controlled. On the other hand, E-UTRAN cannot recognize the presence of a UE that is in the RRCJDLE state. The UE in the RRCJDLE state is managed by a core network in a tracking area (TA) that is a unit of area larger than the cell. That is, for the UE in the RRCJDLE state, only the presence or absence of the UE is recognized in a unit area larger than the cell. For the UE in the RRCJDLE state to be provided with a common mobile communication service, such as a voice service and a data service, the UE must transition to the RRC_CONNECTED state. A TA is distinguished from another TA by its tracking area identity (TAI). A UE can configure the TAI using a tracking area code (TAC), which consists of information transmitted from a cell.
[081] When the user initially turns on the UE, the UE searches for a suitable first cell. The UE then establishes an RRC connection in the cell and records information about it in the core network. After that, the UE remains in the RRCJDLE state. When necessary, the UE that remains in the state
Petition 870190101048, of 10/09/2019, p. 30/97
16/53
RRCJDLE selects a cell (again) and checks the system information or paging information. This operation is called “camping” in a cell. Only when the UE that remains in the RRCJDLE state needs to establish an RRC connection, does the UE establish an RRC connection with the RRC layer of the EUTRAN through the RRC connection procedure and transition to the RRC_CONNECTED state. The UE that remains in the RRCJDLE state needs to establish the RRC connection in many cases. For example, cases may include an attempt by a user to make a phone call, an attempt to transmit data, or the transmission of a response message after receiving a paging message from E-UTRAN.
[082] The non-access layer (NAS) layer positioned over the RRC layer performs functions such as session management and mobility management.
[083] Later in this document, the NAS layer shown in Figure 3 will be described in detail.
[084] Q eSM (Enhanced Session Management) belonging to the NAS layer performs functions such as standard carrier management and dedicated carrier management to control a UE's use of a network PS service. The UE is assigned a standard carrier resource by a specific packet data network (PDN) when the UE initially accesses the PDN. In that case, the network allocates an available IP to the UE to allow the UE to use a data service. The network also allocates QoS from a standard carrier to the UE. LTE supports two types of carriers. One carrier is a carrier that has guaranteed bit rate (GBR) QoS characteristics to guarantee a specific bandwidth for transmitting and receiving data, and the other carrier is a non-GBR carrier that has best effort QoS characteristics without guaranteeing bandwidth. A non-GBR carrier is assigned to the standard carrier. It can be attributed to
Petition 870190101048, of 10/09/2019, p. 31/97
17/53 dedicated carrier a carrier with GBR or non-GBR QoS characteristics.
[085] A carrier allocated to the UE over the network is called an evolved packet carrier (EPS). When the EPS carrier is allocated to the UE, the network assigns an ID. This ID is called an EPS carrier ID. An EPS carrier has maximum bit rate (MBR) and / or guaranteed bit rate (GBR) QoS characteristics.
[086] Figure 5 is a flow chart illustrating a 3GPP LTE random access procedure.
[087] Q random access procedure is used by a UE to obtain UL synchronization with an eNB or to assign an UL radio resource.
[088] Q UE receives a root index and a physical random access channel (PRACH) configuration index from an eNodeB. Each cell has 64 candidate random access preambles defined by a Zadoff-Chu (ZC) sequence. The root index is a logical index used by the UE to generate 64 candidate random access preambles.
[089] The transmission of a preamble of random access is limited to specific time and frequency resources for each cell. The PRACH configuration index indicates a specific subframe and a preamble format in which transmission of the random access preamble is possible.
[090] Q UE transmits a randomly selected preamble to eNodeB at random. The UE selects a random access preamble from 64 candidate random access preambles and the UE selects a subframe corresponding to the PRACH configuration index. The UE transmits the random access preamble selected in the selected subframe.
[091] Measured upon receipt of the preamble of random access, eNodeB sends a random access response (RAR) to the UE. RAR is detected in two
Petition 870190101048, of 10/09/2019, p. 32/97
18/53 steps. First, the UE detects a masked PDCCH with a random access (RA) -RNTI. The UE receives a RAR in a MAC (protocol data unit) PDU (media access control) in a PDSCH indicated by the detected PDCCH.
[092] Figure 6 illustrates a connection procedure in a radio resource control (RRC) layer.
[093] As shown in Figure 6, the RRC status is defined according to whether or not the RRC connection is established. An RRC state indicates whether a UE's RRC layer entity has a logical connection with an eNodeB's RRC layer entity or not. An RRC state in which the UE's RRC layer entity is logically connected to the eNodeB's RRC layer entity is called the RRC connected state. An RRC state in which the UE RRC layer entity is or is not logically connected to the eNodeB RRC layer entity is called an RRC inactive state.
[094] An UE in the Connected state has an RRC connection, so the EUTRAN can recognize the presence of the UE in a cell unit. Consequently, the UE can be efficiently controlled. On the other hand, EUTRAN cannot recognize the presence of an UE that is in an inactive state. The UE in the inactive state is managed by the core network in a tracking area that is a unit of area larger than the cell. The tracking area is a unit of a set of cells. That is, for the UE that is in the inactive state, only the presence or absence of the UE is recognized in a larger area unit. In order for the UE in the idle state to be provided with a common mobile communication service, such as a voice service and a data service, the UE must transition to the connected state.
[095] When the user initially turns on the UE, the UE searches for a suitable first cell and then remains in an inactive state. Only when the UE that
Petition 870190101048, of 10/09/2019, p. 33/97
19/53 remains in the inactive state needing to establish an RRC connection, the UE establishes an RRC connection with the RRC layer of eNodeB through the RRC connection procedure and then transitions to the RRC connected state.
[096] The UE that remains in the inactive state needs to establish the RRC connection in many cases. For example, cases may include an attempt by a user to make a phone call, an attempt to transmit data, or the transmission of a response message after receiving a paging message from E-UTRAN.
[097] For the UE, in the idle state, to establish an RRC connection with eNodeB, the RRC connection procedure needs to be performed as described above. The RRC connection procedure is broadly divided into transmitting an RRC connection request message from the UE to eNodeB, transmitting an RRN connection configuration message from eNodeB to the UE and transmitting a complete RRC connection configuration message from the UE to eNodeB, which are described in detail below with reference to Figure 6.
[098] 1) When the UE in the idle state wishes to establish an RRC connection for reasons such as an attempt to make a call, an attempt to transmit data or an eNodeB response to paging, the UE first transmits a message RRC connection request to eNodeB.
[099] 2) Upon receipt of the UE RRC connection request message, ENB accepts the UE RRC connection request when radio resources are sufficient and then transmits an RRC connection configuration message, which is a reply message to the UE.
[0100] 3) Upon receipt of the RRC connection configuration message, the UE transmits a complete RRC connection configuration message to the
Petition 870190101048, of 10/09/2019, p. 34/97
20/53 eNodeB. Only when the UE correctly transmits the RRC connection configuration message, does the UE establish the RRC connection with eNode B and transition to the RRC connected mode.
[0101] In legacy EPC, MME is categorized into AMF (Core Access and Mobility Management Function) and SMF (Session Management Function) in a Next Generation system (or 5G core network (CN)). Therefore, the interaction of NAS and MM (Mobility Management) with the UE is performed by the AMF, and the SM (Session Management) is performed by the SMF. In addition, SMF manages a UPF (User Plan Function), which is a gateway that has a role in the user plan, that is, to route user traffic. In this case, a part of the S-GW and P-GW control plan in the legacy EPC can be managed by the SMF and a part of the user plan can be managed by the UPF. For routing user traffic, there may be one or more UPFs between the RAN and the DN (Data Network). That is, the legacy EPC can be configured in 5G as illustrated in Figure 7. Also, as a concept corresponding to the PDN connection in the legacy EPS, a PDU (Protocol Data Unit) session is defined in the 5G system. The PDU session refers to the association between a UE, which provides PDU connectivity services of type Ethernet or unstructured type as well as type IP, and a DN. In addition, a UDM (Unified Data Management) performs a function corresponding to the EPC HSS, and the PCF (Policy Control Function) performs a function corresponding to the EPC's PCRF. To satisfy the requirements of the 5G system, the functions can be provided in an extended type. N1 is a reference point for a control plan between 5G EU and AMF, N2 is a reference point for a control plan between 5G (R) AN and AMF, and N3 is a reference point for a user plan between 5G (R) AN and UPF. Also, N4 is a reference point between SMF and UPF, N5 is a reference point between PCF and application function and
Petition 870190101048, of 10/09/2019, p. 35/97
21/53
N6 is a reference point between UPF and a data network. The data network can be a public or private data network outside of a mobile provider, or it can be a data network of a mobile provider. N7 is a reference point between SMF and PCF The details of the 5G system architecture, each function and each interface according to TS 23.501. In particular, the 5G system (ie, next generation system) must support non-3GPP access and, therefore, details such as architecture to support non-3GPP access and network element are described in clause 4.2.7 of TS 23.501 vO.2.0. A prime example of non-3GPP access can include WLAN access, which can include a trusted WLAN and an untrusted WLAN.
[0102] An architecture that includes several types of non-3GPP access is suggested in TS 23.501. For example, AMF (ie, AMF server for EU 3GPP access) for 3GPP access may be different from AMF (ie, server AMF for non-3GPP EU access) for non-3GPP access as shown in Figure 8. This if due to the fact that the PLMNs to / to which the respective accesses belong / are located are different from each other.
[0103] If the number of server AMFs for the UE is 2, the UDM that should store the server AMFs cannot identify an access type of the corresponding server AMF in the case of a service node registration request (for example, operation (Nudm_Serving NF_Registration service) in clause 5.2 .3.1 of TS 23.502v0.3.0) of the AMF. Therefore, if the AMF server for the UE already exists, the UDM cannot determine whether to replace the AMF server or add the AMF server for another access. In addition, when a random network entity queries information in the UE AMF server for the UDM or requests the operating UDM for the AMF server, a problem occurs in which the UDM cannot determine an AMF access type.
[0104] Later in this document, a method will be described for
Petition 870190101048, of 10/09/2019, p. 36/97
22/53 efficiently manage a server AMF or a method to manage information about the server AMF in a state where the AMF can exist through access in relation to 3GPP and non-3GPP access.
Modality [0105] The UDM according to a modality of the present invention can receive a message related to the UE AMF record from the first AMF in a procedure related to an AMF record (Access and Mobility Management Function) , where the message includes access type information and ID (identity) information. The UDM stores the access type information in the AMF and the ID information. If there is a second AMF registered as an UE serving AMF, which corresponds to the type of access information, the UDM can transmit a message related to deregistration to a second AMF. The type of access can include 3GPP access and non-3GPP access. (Access type information related to AMF and ID information can be stored for the case where there is the second AMF registered as the UE serving AMF, which corresponds to the access type information, and the case where there is no there is second MFA).
[0106] That is, the message transmitted to register the AMF as the serving AMF includes the AMF ID and notifies the UDM of information indicating an AMF access type. The UDM stores the MFA ID together with access type information associated with the MFA ID other than the related technique in which the UDM stores only the MFA ID. In this case, the UDM can manage the AMF by type of access and, if the AMF registered as the UE serving AMF, which is the same type of access received, already exists, the UDM unregisters the AMF that was previously registered. The AMF ID included in the message transmitted by the AMF can be one or more of AMF address, AMF NF (Network Function) ID, AMF identifier, AMF IP address, and AMF FQDN and can include type information.
Petition 870190101048, of 10/09/2019, p. 37/97
23/53
NF. Alternatively, the AMF ID can be the GlIAMI type (globally unique AMF identifier). This can be applied to the AMF ID included in a message transmitted from another NF, as well as to a message transmitted from the AMF. Also, this can be applied to the NF ID included in the message transmitted from the NF. The AMF ID, which is stored by the UDM, can be the AMF ID included in the message transmitted from the AMF, or information from a part of the AMF ID, or it can be modified in the format understood by the UDM. This can also be applied to the NF ID, which is stored by the UDM, in the entirety of the present invention.
[0107] The aforementioned operation will be described in detail through a general registration procedure with reference to Figure 9. A general registration procedure for 3GPP TS 23.502v0.3.0 is shown in Figure 9. In Figure 9, step S901, which it relates to the transmission of a UE registration request, to step S913 and the details of steps S915 to S923 will be replaced by the description of the 3GPP TS 23.502v0.3.0 general registry.
[0108] In step S914, if the AMF is changed due to the last registration procedure, if there is no valid signature context for the UE in the AMF, or if the UE provides SUPI (Permanent Signature Identifier) that does not refer to the valid context at AMF, a new AMF starts the Location Update procedure. The new AMF provides the UDM with a type of access that is served. If there is an AMF related to the type of access, this will include that the UDM initiates the cancellation location for that AMF, that is, old AMF. The UDM stores the type of access related to the AMF server (information) together with the AMF server (information). (The details of the operation that the new AMF provides to the UDM information on the type of access and the related UDM operation will be understood with reference to the description made in Figure 11). The old AMF notifies MM context deletions and notifies all possible and associated SMFs in the MM context
Petition 870190101048, of 10/09/2019, p. 38/97
24/53 deleted, and the new AMF generates MM context for the UE after obtaining AMF-related signature data from the UDM. At present, the old AMF can delete the context ΜΜ related to a 3GPP access and report the deleted MM context to the SMF (s) for PDU session on a 3GPP access. The new MFA can generate MM context for 3GPP access. The old AMF and the new AMF recognize that the type of access is 3GPP access. This is due to the fact that the access obtained from the UDM or served by the UDM is only 3GPP access.
[0109] In this procedure, if the UE is registered in the same AMF already registered in a non-3GPP access (for example, if the UE is registered in a non-3GPP access and initiates this registration procedure to add a 3GPP access), the UE it must transmit an AMF Request Notification message (AMF ID, type of access) to the UDM. The type of access is defined as “3GPP access” and the Notification Request is used to register a server AMF for 3GPP access in the UDM. The UDM transmits a Notification Reply message to the MFA. As described above, although the AMF can notify the addition of UDM for a new access via the Notification Request message, several messages, such as the Update Location Request message, can be used.
[0110] A registration procedure through an untrusted non-3GPP access is shown in Figure 10. After step S1007, steps S913 and S914 in Figure 9 are performed. Although the description in Figure 9 is based on the fact that the type of access is 3GPP access, this description will be given based on the fact that the type of access is non-3GPP access. Steps S913 and S914 can be performed before step S1007. In addition, the detailed description of each procedure in Figure 10 will be replaced by the description of Registry via 3GPP TS 23.502v0.3.0 Non-3GPP Unreliable Access.
[0111] A service information flow / service operation operation
Petition 870190101048, of 10/09/2019, p. 39/97
25/53
Nudm_Serving NF_Registration is shown in Figure 11. In this case, the Nudm_Serving NF_Registration service can be specified as mentioned in Table 2 below. In the following description, the scope of the present invention is not limited to a specific name.
[TABLE 2]
Service name or service operation: Nudm_Serving NF_Registration Description: Register the UE serving NF in the UDM
Known NF Consumers: AMF, SMF, SMSF
Simultaneous use: No.
Prerequisite conditions: No
Postconditions: UDM stores the Requestor NF ID in the UE context.
Entries, Required: Requestor NF ID, SUPI.
Entries, Optional: subscription data recovery indication.
Outputs, Required: Result indication.
Outputs, Optional: UE signature data is retrieved by the Requestor's NF ID, if the signature data recovery indication is included.
[0112] With reference to Figure 11, in step S1101, a Requestor NF wishes to be registered in the UDM as an UE serving NF. The requesting NF transmits a Request for NF Registration EU Server (SUPI, NF ID) message to the UDM. The NF ID indicates the type and NF ID of the serving NF. Selectively, according to the Requestor's type of NF, the request message may include additional information stored in the UDM. For example, if the NF is SMF, the NF type can include related APN.
[0113] If the Requester's type is AMF, the Request message includes the type of access (for example, “3GPP access” or “Non-3GPP access” stored together with AMF (information) in the UDM.
[0114] The AMF can perform step S1101 by type of access. For example, if UE # 1 is registered in AMF # 1 through 3GPP access, AMF # 1 transmits the
Petition 870190101048, of 10/09/2019, p. 40/97
26/53 Request message, which includes the type of access = “3GPP access”, to the UDM. Subsequently, if UE # 1 is registered with AMF # 1 through non-3GPP access, AMF # 1 transmits the Request message, which includes the type of access = “Non-3GPP access”, to the UDM. As another example, if UE # 2 is registered in AMF # 2 through 3GPP access, AMF # 2 transmits the Request message, which includes the type of access = “3GPP access”, to the UDM. Subsequently, if UE # 2 is registered in AMF # 3 through non-3GPP access, AMF # 3 transmits the Request message, which includes the type of access = “Non-3GPP access”, to the UDM.
[0115] Although the above description is provided based on the fact that the access type information is “3GPP access” or “Non 3GPP access”, the access type information can be expressed in the form of several levels / formats . For example, 3GPP access can be expressed as NG-RAN (or NR) or E-UTRAN (or LTE). Also, 3GPP access can be expressed as your detailed RAN. Non-3GPP access can be expressed as untrusted non-3GPP access, untrusted non-3GPP access, WLAN, etc. Also, non-3GPP access can be expressed as your detailed access. Also, the type of access can indicate all types of access as "All accesses" or "Both accesses. Thus, if the type of access indicates all types of access and step S1101 is performed, AMF may delay step S1101 until AMF recognizes that AMF is a serving AMF for all types of access. Also, the type of access information can be implicitly indicated. For example, the RAT type can be inferred through location information (Cell ID, WLAN AP SSID, etc.) from the UE. Also, access type information can be interpreted as RAT type information. The description and operation related to the type of access can be applied to the present invention as is, or can be applied to it by modification.
[0116] The MFA may include information on the type of access in the
Petition 870190101048, of 10/09/2019, p. 41/97
27/53
Request for all UEs (ie always). Alternatively, the MFA may include information on the type of access in the Request message if one or more of the following conditions are met. This is applied to the present invention.
[0117] i) The case where the UE can receive a service through non-3GPP access (or. WLAN).
[0118] ii) The case where the UE can perform the handover for non-3GPP (or WLAN) access.
[0119] iii) The case where the PLMN in / to which the MFA is located / belongs does not support non-3GPP (or WLAN) access.
[0120] iv) The case where the PLMN in / to which the AMF is located / belongs does not support / includes N3IWF.
[0121] The case where the type of access served by the MFA is 3GPP access may not include information on the type of access. In this case, the UDM may consider that the access associated with the MFA is 3GPP access. In addition, in this case, as the type of access indicates that the type of access is only non-3GPP access, the flag (or bit) is given to 1 or Yes or Set, so it can indicate that the AMF operates the access not 3GPP. If the access type information includes the flag, this may indicate that the AMF operates non-3GPP access. (For example, the flag name is given to N3GPP Flag). This is applied to the present invention.
[0122] Optionally, if the access type information includes indication of recovery of signature data, the Requesting NF will request the UDM to return UE subscription data related to the NF type from the reply message. This indication is implicitly reported by (UDM_Subscription DataJJpdateNotification, see Figure 18) when the data is no longer changed or synchronized.
[0123] When the Requestor NF transmits a Request message
Petition 870190101048, of 10/09/2019, p. 42/97
28/53 of NF Registration EU server to UDM, it implicitly notifies the change (for example, services “Nudm_Serving NF_ChangeNotification” and “Nudm_Subscription Data_UpdateNotification”) of ID de. The subscription to this notification service can be a subscription of the corresponding type of access.
[0124] In step S1102, the UDM stores a registered server NF in the context of UE. The type of NF related to the subscription data resumes for the Requestor NF if the indication of recovery of subscription data is included in the request message.
[0125] If the registered server NF is the AMF, the UDM stores the type of access associated with the server NF. If the AMF related to the type of associated access exists in the UDM in relation to the UE, the UDM replaces the existing AMF with the new AMF, that is, Requestor NF. In that case, the UDM can also transmit a location cancellation message to the existing AMF. Finally, if the AMF for the associated access type does not exist in the UDM, the UDM stores new AMF information (the Requestor NF with the access type).
[0126] However, if the UDM receives a request message related to the UE context deletion from the NF and the NF is AMF, the request message related to the UE context deletion can include access type information. In this sense, a flow of information service / service operation of the Nudm_ Subscriber Data_ Purge service is shown in Figure 12 (a).
[0127] In step S1201, the Requestor NF transmits a UE Data Clear (SUPI) request message to the UDM. This is a request to allow the UDM to delete the stored Requestor NF from the UE context. When the Requestor NF transmits the UE Data Clear request message, an associated type of NF access can be included in this message. The associated access type can be included in the message only when the NF is the MFA. Also, the type of access information can be
Petition 870190101048, of 10/09/2019, p. 43/97
29/53 included in the message only in the case of non-3GPP access.
[0128] In step S1202, the UDM removes the Requestor NF from the UE context and responds to the Requestor NF as an EU Clear response. Subsequently, the UDM no longer transmits notifications of update of subscription data to the requester. The UDM deletes the Requestor NF from the UE context in relation to the type of access related to the type of access information, that is, the type of access requested (or type of access considered requested) based on the type of access information included or not included in the request message. At that time, the type of access information may be included in the response.
[0129] In the above description, Nudm_ Subscriber Data_ Purge can be specified as mentioned in Table 3 below.
[TABLE 3]
Service name or service operation: Nudm_ Subscriber Data_ Purge Description: UDM deletes information related to the Requestor's NF in the context of UE.
Known NF Consumers: AMF, SMF, SMSF
Simultaneous use: No.
Prerequisite conditions: None
Postconditions: UDM deletes information related to the Requestor NF in the context of UE.
Inputs, Required: SUPI Inputs, Optional: None Outputs, Required: Result Indication. Exits, Optional: None [0130] However, whenever a user profile is changed in the UDM and whenever the change affects an AMF user profile, the UDM notifies the AMF
Petition 870190101048, of 10/09/2019, p. 44/97
30/53 affected by the change of changes through a procedure “Subscriber Data Update Notification for AMF”. In this case, AMF adds or changes the user profile. When the UDM performs the Subscriber Data Update Notification operation in the AMF, information indicating an access type for a user profile change can be provided to the AMF. If the AMF serving 3GPP access is different from the AMF serving non-3GPP access, the UDM performs the Subscriber Data Update Notification operation in the AMF for the AMF serving the access related to changing user profile . The “Subscriber Data Update Notification” service is used to allow the UDM to update subscriber data stored in the AMF.
[0131] The AMF starts an appropriate operation according to the changed subscriber data. For example, if the updated subscription data indicates that the UE is not enabled for roaming within a network, AMF initiates an AMF initiated deregistration procedure. If the AMF is operating an access, even if there is no information, the AMF performs an appropriate operation related to the changed subscriber information in relation to the access based on information about the type of access provided by the UDM.
[0132] An AMF procedure subscriber data cleanup is shown in Figure 12 (b). In step S1211, after the MM context and the subscriber data for an unregistered UE is removed, the AMF transmits a UE Clear message (SUPI) to the UDM. When the AMF transmits the UE Clear message to the UDM, an access type of the UE clear message can be included in this message either explicitly or implicitly. If the access type of the UE clearing message is explicitly included in the message, the access type can be included in the message in the form of 3GPP access, non-3GPP access and information indicating two accesses. If the access type of the EU clear message is implicitly included in the
Petition 870190101048, of 10/09/2019, p. 45/97
31/53 message, the type of access can be notified including location information of the UE. For example, information like cell ID can be interpreted as 3GPP access, and information like WLAN AP SSID can be interpreted as non-3GPP access. If both accesses are cleared, the location information for both accesses may be included in the corresponding information.
[0133] In step S1212, the UDM sets an UE clear flag and responds via an EU Clear Confirmation message. The UDM can manage the UE Clear flag by type of access. Therefore, the UDM sets the UE Clean flag related to clean access based on the information provided by the AMF, information on the access served by the AMF, etc.
[0134] A service information flow / service operation of the Nudm_Serving NF_RemoveNotification service is shown in Figure 13. In step S1301, if the UDM detects that the UE serving the NF has been removed (for example, a new AMF is registered in the UDM ), the UDM notifies the Requestor NF previously enrolled in the Nudm_Serving NF_RemoveNotification service of the result detected through UE Server NF Removal Notification (SUPI, reason for removing the server NF). The reason for removing the provided server NF indicates the reason why the NF was removed (for example, update due to a new registered NF server). The Requestor NF can additionally perform a related process. (For example, removing the context of the UE that maintains it when the UE is not served by the requester). The UDM can perform the above operation to suit the type of access served by the AMF. That is, if the Requestor NF is enrolled in the Nudm_Serving NF_RemoveNotification service for a specific type of access, and when the UE server NF related to the corresponding access type is removed, it can be notified to the Requestor NF. In this
Petition 870190101048, of 10/09/2019, p. 46/97
At the moment, the associated access type of the NF server can be added to the EU NF Server Removal Notification message.
[0135] In the above description, Nudm_Serving NF_RemoveNotification can be specified as mentioned in Table 4 below.
[TABLE 4]
Service name or service operation: Nudm_Serving NF_RemoveNotification Description: UDM notifies the Requestor NF, which has already signed the removal notification, the Requestor NF ID has been removed from the UDM due to a new UE server NF registered in the UDM.
Known NF Consumers: AMF, SMF, SMSF
Simultaneous use: No.
Prerequisite conditions: UDM detects that the UE service NF has been removed. Postconditions: None.
Entries, Required: NF server registered in UDM implicitly / explicitly
Inputs, Optional: None.
Outputs, Required: SUPI, reason for changing NF server SUPI, reason for removing NF server.
Exits, Optional: None [0136] However, if the UDM transmits the deregistration message due to the withdrawn subscription, the UDM can indicate a type of message access related to deregistration.
[0137] The operation described above will be described in detail through a UDM initiated deregistration procedure with reference to Figure 14. The 3GPP TS 23.502v0.3.0 deregistration procedure is shown in Figure 14. In Figure 14 , the details after step S1403 will be replaced by the description of 3GPP deregistration procedures
Petition 870190101048, of 10/09/2019, p. 47/97
33/53
TS 23.502v0.3.0.
[0138] In step S1401a, if the UDM wishes to immediately delete MM contexts and subscriber PDU sessions, the UDM must transmit a Location Cancellation message (SUPI (Permanent Subscriber Identifier), Cancellation Type) together with a type of cancellation cancellation for which the Withdrawal Subscription is configured in relation to the registered AMF.
[0139] When the UDM transmits the Cancel Location message, the UDM can add an access type to a cancellation request. The UDM can add the above information only if the MFA is operating both 3GPP and non-3GPP access. If the AMF is operating both accesses, although the information above is not included therein, the AMF may consider that: i) a cancellation request for all accesses served by the AMF is transmitted from the corresponding UE; ii) a cancellation request only for 3GPP access is transmitted and iii) a cancellation request only for non-3GPP access is transmitted. This can be considered as i), ii) or iii) based on information such as local configuration, operator policy, etc. included in the MFA.
[0140] If a server AMF for 3GPP access is different from a server AMF for non-3GPP access, the UDM transmits the Location Cancellation message to the AMF related to an access whose cancellation must be requested. If both accesses are canceled (it can be considered that the cancellation must be carried out independently of access), the Location Cancellation message must be transmitted to each of the two AMFs. If there is information indicating a type of access to a cancellation request, AMF can determine the type of access to the cancellation request based on the information. Or, even if there is no information indicating a type of access for a cancellation request, since the
Petition 870190101048, of 10/09/2019, p. 48/97
34/53
AMF knows a type of access served by itself, AMF can determine the type of access of the cancellation request.
[0141] In step S1402, if the Cancellation Type is a Removed Subscription, the MFA that has the UE context active notifies a UE that is in CM-CONNECTED state of the fact of the canceled registration, transmitting the Cancellation Request message. Registration (Cancellation Type) to the UE. If the Cancellation of Location message includes a flag indicating that a reconnection is required, the AMF must configure an Unsubscribe Type to indicate that a reconnection is required. If the UE is in the CM-IDLE state, the MFA pages the UE. As described above, since the AMF can recognize the type of access for which cancellation is requested or the type of access determined to be canceled, the AMF performs a de-registration operation from the UE for the corresponding access. If registration cancellation is performed for both 3GPP and non-3GPP access, AMF may notify explicitly or implicitly that registration cancellation must be performed for two accesses while transmitting the Registration Cancellation Request to one access.
[0142] However, if a message to request AMF server information is received from the NF, the UDM transmits AMF server information related to the type of access to the NF, and the request message for the AMF server information can include information of the server type. access.
[0143] In this sense, a service information flow / service operation of the Nudm_ Serving NF_Get service is shown in Figure 15 (a).
[0144] In step S1501, the NF consumer transmits a Get UE Server NF Request message (UE ID, type NF) to the UDM to obtain an UE server NF. The type of NF indicates which type of NF (for example, AMF, SMF, etc.) was consulted. When the NF consumer (ie Requestor) transmits the
Petition 870190101048, of 10/09/2019, p. 49/97
35/53 message Get NF Server Request from UE, the NF consumer can include information associated with the type of access of the serving NF in this message. This type of access information can be included in the corresponding message only if the type of NF is AMF. Also, the type of access information can be included in the corresponding message only in case of non-3GPP access.
[0145] In step S1502, the UDM checks whether the Requesting NF is enabled to access required subscriber server NF data. If applicable, the UDM provides the requester with the required subscriber server NF (for example, FQDN or server NF address). The UDM provides the UE server NF regarding the type of access related to the type of access information, that is, the type of access requested (or type of access considered requested) based on the type of access information included or not included in the request message. At that time, the type of access information may be included in the response.
[0146] The UDM can unconditionally provide the MFA ID related to 3GPP access to the response if the request message from step S1501 is received. This can be interpreted as the details about the access type information suggested as above are not supposed to be added.
[0147] In this case, the Nudm_ Serving NF_Get service can be specified as mentioned in Table 5 below. In the following description, the scope of the present invention is not limited to a specific name, etc.
[TABLE 5]
Service name or service operation: Nudm_ Serving NF_Get Description: The Requesting NF requests the UDM to obtain the UE serving server. Known NF Consumers: NEF
Simultaneous use: No.
Petition 870190101048, of 10/09/2019, p. 50/97
36/53
Prerequisite conditions: None
Postconditions: None.
Entries, Required: EU ID, NF Type
Inputs, Optional: None
Outputs, Required: SUPI, Server NF ID of the type of NF requested by Requestor NF.
Outputs, Optional: None [0148] Service information flow / service operation of the Nudm_Subscriber Data_Get service is shown in Figure 15 (b).
[0149] In step S1511, the Requestor NF requests the corresponding subscriber data from the UDM while providing the EU ID (for example, SUPI) and NF type information.
[0150] In step S1512, if the NF type is SMF, DNN is also included. When the Requestor NF transmits the Get Subscriber Data Request message, the Requestor NF may include information about the type of access in this message. The type of access information can be included in the corresponding message only if the NF is AMF. Also, the type of access information can be included in the corresponding message only in case of non-3GPP access [0151] In step S1512, the UDM checks the EU ID and the NF type to retrieve the corresponding subscriber data and provide the data to the Requestor NF. If the Requestor's NF is SMF, the subscriber's data includes PDU type (s), auto-enabled SSC mode (s), Standard QoS profile, etc., for example. The UDM provides the Requestor NF with subscriber information about the type of access related to the type of access information, that is, the type of access requested (or type of access considered requested) based on the type of access information included or not included in the request message. At that moment, the
Petition 870190101048, of 10/09/2019, p. 51/97
37/53 access type information may be included in the response.
[0152] In this case, Nudm_Subscriber Data_Get can be specified as mentioned in Table 6 below. In the following description, the scope of the present invention is not limited to a specific name, etc.
[TABLE 6]
Service name: Nudm_Subscriber Data_Get Description: Requestor NF gets subscriber data from UDM Known NF consumers: SMF, SMSF, AMF, AUSF Simultaneous use: No.
Prerequisite conditions: None Post-conditions: None Entries, Required: SUPI, NF type. Entries, Optional: DNN if the NF type is SMF. Exits, Required: The Requestor NF obtains the requested subscription data. Exits, Optional: None [0153] However, the UDM may receive a request to request NF UE reachability information, where the request to request UE reachability information may include access type information. The UDM can be subscribed to a notification service for EU AMF reachability event related to the type of access. If information indicating that the UE is accessible is received from the MFA related to the type of access, the UDM can transmit the information indicating that the UE is accessible, to the NF.
[0154] The operation described above will be described in detail using Accessibility procedures with reference to Figure 16. The Accessibility procedures for 3GPP TS 23.502v0.3.0 are shown in Figure 16.
[0155] In step S1600, in the registration procedure or in the signature update procedure, the UDM notifies the MFA of identities (for example,
Petition 870190101048, of 10/09/2019, p. 52/97
38/53
FQDNs) of network entities on which the UE reachability notification request is granted. UDM and SMSF are basically granted.
[0156] When the UDM notifies the AMF of network entity (ies) that have requested / requested UE reachability notification, the UDM can provide a type of access desired by each network entity to obtain a reachability notification service. The type of access can be determined based on the associated information provided by each network entity, information (local configuration, operator policy, etc.) configured in the UDM, type / property of the entity (for example, service provided by the entity) and UE subscriber information. The UDM can provide the above information only if the AMF is operating both 3GPP and non-3GPP access. If the AMF is operating both accesses, although the above information is not included in it, the AMF may consider that: i) a reachability notification request for all accesses served by the AMF is transmitted from the corresponding UE; ii) a reachability notification request only for 3GPP access is transmitted and iii) a reachability notification request only for non-3GPP access is transmitted. This can be considered as i), ii) or iii) based on local configuration, operator policy, UE subscriber information, etc. included in the MFA.
[0157] If a server AMF for 3GPP access is different from a server AMF for non-3GPP access, the UDM transmits a message indicating the network entity to the AMF related to an access whose UE reachability notification must be requested. If there is information indicating a type of access to a reachability notification request, AMF can determine the type of access to a reachability notification request based on the information. Or, even if there is no information indicating an access type of a reachability notification request, since the MFA
Petition 870190101048, of 10/09/2019, p. 53/97
39/53 knows a type of access served by itself, the MFA can determine the type of access of the reachability notification request.
[0158] AAMF can store access type information indicating an access type for each entity that has requested an EU reachability notification, along with the entity ID.
[0159] In step S1601, if a service-related entity requests the UDM to provide a UE reachability notification, the UDM verifies that the entity has been granted to execute the request at the subscriber. If the entity has not been granted, the request is rejected (for example, if the requesting entity is recognized as a valid entity, but not authorized for that subscriber) or the request is disregarded. (For example, if the requesting entity is not recognized). An appropriate O&M report is generated.
[0160] When the service-related entity requests the UE reachability notification UDM, an access type of a reachability notification service that you want to receive can be added to the request. If the above information is not included in the request, the UDM may consider that: i) a notification request for all accesses is transmitted from the corresponding UE; ii) a notification request for 3GPP access only is transmitted; and iii) a notification request for non-3GPP access only is transmitted. This can be considered as i), ii) or iii) based on the local configuration, operator policy, type / property (for example, service provided by the entity) that requested reachability notification, UE subscriber information, etc. included in the UDM.
[0161] The UDM can store access type information indicating an access type for each entity that requested an EU reachability notification, along with the entity ID.
[0162] In step S1602a, the UDM stores the entity's identity
Petition 870190101048, of 10/09/2019, p. 54/97
40/53 related to the service and defines the URRP-AMF parameter as the receipt of the request. If a value of the URRP-AMF parameter is changed from “not defined” to “defined”, the UDM transmits UE-REACHABILITY-NOTIFICATION-REQUEST (URRPAMF) to the AMF. When the UDM requests the UE reachability notification AMF, the UDM can provide an access type of the reachability notification service that it wants to receive. This type of access can be determined based on the type of access information received from the entity that requested the UDM for the UE reachability notification, information (local configuration, operator policy etc.) configured in the UDM, type / property (for example , entity-provided service) of the entity, UE subscriber information, etc. The UDM can provide the above information only if the MFA is serving both 3GPP and non-3GPP access. If the AMF is serving both accesses, although the information above is not included in it, the AMF may consider that: i) a reachability notification request for all accesses served by the AMF is transmitted from the corresponding UE; ii) a reachability notification request only for 3GPP access is transmitted and iii) a reachability notification request only for non-3GPP access is transmitted. This can be considered as i), ii) or iii) based on local configuration, operator policy, UE subscriber information, etc. included in the MFA.
[0163] If a server AMF for 3GPP access is different from a server AMF for non-3GPP access, the UDM transmits the request message to the AMF related to an access whose UE reachability notification must be requested. If there is information indicating a type of access to a reachability notification request, AMF can determine the type of access to a reachability notification request based on the information. Or, even if there is no information indicating a type of access for a request for
Petition 870190101048, of 10/09/2019, p. 55/97
41/53 reachability notification, since the AMF knows a type of access served by itself, the AMF can determine the access type of the reachability notification request.
[0164] The URRP-AMF parameter managed by the UDM can be managed by access. For example, if a random entity requests an EU reachability notification for 3GPP access, the URRP-AMF parameter for 3GPP access is defined as defined.
[0165] AAMF can store access type information indicating an access type of the UDM that requested a UE reachability notification, along with the entity ID.
[0166] In step S1602b, SMSF transmits UE-REACHABILITYNOTIFICATION-REQUEST (URRP-AMF) to AMF When SMSF requests the EU reachability notification AMF, SMSF can add an accessibility notification service access type that want to receive. If the above information is not included in the request, the MFA may consider that: i) a notification request for all accesses is transmitted from the corresponding UE; ii) a notification request for 3GPP access only is transmitted; and iii) a notification request for non-3GPP access only is transmitted. This can be considered as i), ii) or iii) based on local configuration, operator policy, UE subscriber information, etc. included in the MFA. Alternatively, if the above information is not included in the request, AMF may consider that a 3GPP access notification request is transmitted, as SMSF is a function that is responsible for SMS. The AMF can store access type information indicating an access type of the SMSF that requested an EU reachability notification, along with the SMSF ID [0167] In step S1603, the AMF verifies that a requesting entity has been
Petition 870190101048, of 10/09/2019, p. 56/97
42/53 granted to execute the subscriber's request. If the entity has not been granted, the request is rejected (for example, if the requesting entity is recognized as a valid entity, but not authorized for that subscriber) or the request is disregarded. (For example, if the requesting entity is not recognized). An appropriate O&M report is generated.
[0168] If the AMF has an MM Context for the corresponding user, the AMF configures URRP-AMF to indicate that it is necessary to report UDM information regarding changes in UE reachability. (For example, when the next NAS activity with which the UE is detected).
[0169] The URRP-AMF parameter managed by the AMF can be managed by access. For example, if the UDm requests an EU reachability notification regarding 3GPP access, the UDM defines the URRP-AMF parameter for 3GPP access as defined.
[0170] Since the UDM receives the UE reachability notification request from another network entity or when the UDM selects / determines that the AMF executes the UE reachability request, the UDM can transmit the reachability notification request from UE to the AMF by selecting / unconditionally determining the AMF that is serving 3GPP access in relation to the corresponding UE (when steps S1600 and 1602a are performed). It can be interpreted that the MFA related to 3GPP access is selected / determined when there are a plurality of MFAs that are serving the UE.
[0171] A NudmJJE Reachability_Notification service information / service operation flow is shown in Figure 17. In step S1701, the requester NF transmits the UE reachability signature message to provide information such as EU ID and Optional Parameters to the UDM. The UE ID (for example, SUPI) must identify the UE by the UDM. When the Requestor NF
Petition 870190101048, of 10/09/2019, p. 57/97
43/53 transmit the EU Accessibility Signature message, the type of access information may be included in this message. Access type information can be included in the message only when the NF is the MFA. Also, the type of access information can be included in the message only in case of non-3GPP access.
[0172] In step S1702, the UDM can selectively grant the requester based on the NF identities included in the Optional Parameter. If the requester's NF is not allowed to use this service, the UDM transmits a Reject Response.
[0173] In step S1703, if the Requestor NF has permission to access this service, the UDM transmits the UE Reachability Notification message to the requestor NF as soon as it acquires that the UE is reachable. The UDM provides the Requestor NF with reachability information from the UE on the type of access related to the type of access information, that is, the type of access requested (or type of access considered requested) based on the type of access information included or not included in the request message. At that time, the type of access information may be included in the response. For example, if the Requestor NF is considered to perform the UE Accessibility Signature for 3GPP access, the UDM detects that the UE is reachable on 3GPP access and reports the detected result to the Requestor NF.
[0174] If the UDM receives the Sign message from step S1701, the UDM can be considered unconditionally subscribes to the EU reachability notification service for 3GPP access. This can be interpreted as it is assumed that the details about the type of access information suggested in step S1701 have not been added.
[0175] In this case, NudmJJE Reachability_Notification can be specified as mentioned in Table 7 below. In the following description, the scope
Petition 870190101048, of 10/09/2019, p. 58/97
44/53 of the present invention is not limited to a specific name, etc.
[TABLE 7]
Service name: Nudm_UE Reachability_Notification
Description: The Requestor NF subscribes to the service that, once the UE becomes reachable, the requestor NF can be notified by the UDM.
Known NF consumers: NEF.
Simultaneous use: No.
Prerequisite conditions: None
Postconditions: None Entries, Required: EU ID Entries, Optional: Optional Parameters. Exits, Required: UDM Notifies the Requestor NF when the corresponding UE is reachable
Exits, Optional: None [0176] However, a service information flow / service operation for the Nudm_Subscription Data_UpdateNotification is shown in Figure 18. In step S1801, the UDM transmits the Subscriber Data Update Notification (SUPI, Data Subscription) to the Requestor NF previously registered in the UDM through the previous Nudm_Serving NF_Registration. If there is a plurality of Requestor NFs in relation to the UE (for example, two server AMFs in relation to the UE, where one is AMF for 3GPP access and the other is AMF for non-3GPP access), the UDM performs the operation of the step S1801 for all Requestor NFs.
[0177] The UDM can perform the above operation to suit the type of access served by the AMF. That is, if the subscriber information for a specific type of access is changed, the UDM can report the changed subscriber information to the Requestor NF related to the corresponding type of access.
Petition 870190101048, of 10/09/2019, p. 59/97
45/53
At that time, the type of access whose subscriber information has been changed can be added to the Subscriber Data Update Notification message.
[0178] For example, if the subscriber information for a non-3GPP access is changed, the UDM can report the changed subscriber information to the AMF related to that access. This means that the report is not provided to the AMF related to 3GPP access if the corresponding AMF exists. In this case, Nudm_Subscription Data_UpdateNotification can be specified as mentioned in Table 8 below. In the following description, the scope of the present invention is not limited to a specific name, etc.
[TABLE 8]
Service name or service operation: Nudm_Subscription Data_UpdateNotification
Description: UDM notifies the NF consumer of UE Subscriber Data updates.
Known NF Consumers: AMF, SMF, SMSF
Simultaneous use: No.
Prerequisite conditions: UDM detects whether UE subscription data is up to date
Postconditions: None.
Entries, Required: NF server registered in UDM implicitly / explicitly for notification.
Inputs, Optional: None.
Outputs, Required: SUPI, Signature data updated
Outputs, Optional: None [0179] The UE Activity Notification procedure is shown in Figure 19. With reference to Figure 19, in step S1901, the MFA receives a
Petition 870190101048, of 10/09/2019, p. 60/97
46/53 UE reachability indication (for example, Registration Request message or UE Service Request message, or RAN EU reachability indication). The RAN can be the RAN related to 3GPP access, or N3IWF.
[0180] In step S1902, if the AMF includes the MM context of the UE and URRP-AMF for the UE is configured to report immediately if the UE is reachable, the AMF transmits the UE Activity Notification message (Permanent ID, Reachable per EU) to the UDM (step S1902a) or SMSF (step S1902b) and clear the corresponding URRP-AMF.
[0181] If the AMF manages the URRP-AMF parameter by access and if the URRP-AMF for the access to which the UE is reachable is defined as “defined”, a message reporting that the UE is active can be transmitted to an entity (e.g. UDM, SMSF, etc.) that requested EU reachability notification in relation to the corresponding access. At that time, the message may include an access for which the UE is reachable. However, even if the message does not include access information, since the entity like the UDM knows that the AMF is an AMF serving for corresponding access, the entity can determine an access for which the UE is reachable. Subsequently, the AMF clears the URRP-AMF for the corresponding access.
[0182] In step S1903, if the UDM receives the UE Activity Notification message (Permanent ID, Accessible by UE) or the Update Location message for a UE that has the URRP-AMF defined, the UDM triggers appropriate notifications for the entities that sign these notifications and clears the URRP-AMF for the UE.
[0183] If the UDM receives a report message indicating that the UE becomes active, from the MFA, the UDM can transmit a message stating that the UE is active to the entity that requested the UE reachability notification
Petition 870190101048, of 10/09/2019, p. 61/97
47/53 in relation to the corresponding access (the method for identifying the access is described in step S1902). At that time, the message may include an access for which the UE is reachable. If the UDM manages the URRP-AMF parameter by access, the UDM clears the URRP-AMF for access for which the UE is reachable.
[0184] However, the 5GS handover to EPS for single registration mode with the 3GPP TS 23.502v0.3.0 Nx interface procedure is shown in Figure 20. The Nx interface is an interface between AMF and MME for the interaction of 5GS and EPS. The details of each step in Figure 20 will be replaced by the 5GS handover description for EPS for single registration mode with the 3Gxp TS 23.502v0.3.0 Nx interface.
[0185] The MME can perform the Update Location operation together with HSS (this can be interpreted as HSS + UDM, and can be called UDM). This serves to notify the HSS that the MME has become a server node for the UE. Therefore, the MME transmits the Location Update Request message to the HSS, and the HSS that received the Location Update Request message performs a Location Cancellation operation together with the AMF. The AMF on which the HSS performs the Location Cancellation operation is the AMF related to 3GPP access. That is, if the UE performs the handover of 5GS to EPS, the location cancellation by the HSS and the UDM can be performed for AMF whose access type is 3GPP. For example, if there is AMF # 1 associated with 3GPP access in relation to the corresponding UE and AMF # 2 associated with non-3GPP access, AMF performs the Location Cancellation operation together with AMF # 1. (Details of the Location Cancellation will be understood with reference to the details described in the Nudm_Serving NF_RemoveNotification service).
[0186] Contrary to the above case, if the MME transmits the Update Location Request message to the HSS, the HSS can maintain the AMF
Petition 870190101048, of 10/09/2019, p. 62/97
48/53 related to 3GPP instead of canceling the MFA. The MME Location Update operation may or may not be caused by the UE TAU operation. (The Update Location operation and the Cancel Location operation in EPS will be understood with reference to TS 29.272.) [0187] The description above can be extensive or equally applied to another scenario in which the UE changes the 5G system system for EPS, as well as the procedure shown. Also, the above description can be applied both to cases where the UE changes the 5G system to EPS in an inactive mode and to the case where the UE changes the 5G system to EPS in a connected mode. For example, if the UE that is in idle mode (or if the UE in idle mode) changes from 5GS to EPS, the UDM can perform the Location Cancellation operation for the AMF whose access type is 3GPP, that is, it can transmit a deregistration message to the AMF.
[0188] Also, the above description can be applied both to the case where the UE is SR (Single Record: registered in only one system) and to the case in which the UE is DR (Dual Record: registered in two systems). Also, the above description can be applied both to the case where there is an interface (Nx interface) between the 5G System and the EPS and to the case where there is no interface.
[0189] However, the handover from EPS to 5GS using the 3GPP TS 23.502v0.3.0 Nx interface procedure is shown in Figure 21.
[0190] With reference to Figure 21, in step S2101, the originating E-UTRAN determines that the UE must perform the handover to 5G-RAN. E-UTRAN transmits the Handover Required message (Node ID 5G-RAN of destination, Transparent Container of Origin to Destination) to the MME.
[0191] In step S2102, MME selects a target AMF and transmits the Request for Relocation Request Nx (Destination node ID 5G-RAN, Transparent Source to Destination Container, EPS MM Context, information
Petition 870190101048, of 10/09/2019, p. 63/97
49/53 PDN Connection) to the MFA.
[0192] When the MME selects the target AMF, the MME can consult the HSS (this can be interpreted as HSS + UDM and can be called UDM). If the serving AMF for the UE already exists, the HSS can provide MME with information indicating that the serving AMF exists. At that time, HSS can be provided only if the serving AMF and MME belong to the same PLMN. Unlike this case, PLMN information can be provided to MME together with the serving AMF, so that PLMN information can be used so that the MME can select / determine the destination AMF. Also, the HSS can provide information (for example, AMF ID) in the AMF even in the event that the serving AMF is AMF related to non-3GPP access. If the AMF server for the UE exists for 3GPP access and non-3GPP access, the HSS can provide AMF server information related to 3GPP access.
[0193] Details of the other steps S2103 to S2118 will be replaced by the 5GS handover description for EPS for single registration mode with the 3GPP TS 23.502v0.3.0 Nx interface.
[0194] With reference to Figure 21, the MFA can perform the Update Location operation together with UDM (this can be interpreted as HSS + UDM, and can be called UDM). This serves to notify the UDM that the AMF has become a server node for the UE. If the AMF performs the Location Update operation (or the operation described in the Nudm_Serving NF_Registration service in Figure 11) for the UDM, the UDM performs the Location Cancellation operation together with the MME. In contrast to this case, the UDM can maintain the MME instead of canceling the MME.
[0195] The above description can be extensive or equally applied to another scenario in which the UE changes the system from the 5G system to EPS, as well as the procedure shown. Also, the above description can be applied to both
Petition 870190101048, of 10/09/2019, p. 64/97
50/53 cases in which the UE changes the 5G system to EPS in an inactive mode as in the case in which the UE changes the 5G system to EPS in a connected mode. Also, the above description can be applied both to the case where the UE is SR (Single Record: registered in only one system) and to the case in which the UE is DR (Dual Record: registered in two systems). Also, the above description can be applied both to the case where there is an interface (Nx interface) between the 5G System and the EPS (interface between MME and AMF) and to the case where there is no interface.
[0196] Although the operation suggested as above has been described based on the fact that the NF (Network Function) is MFA, without limitation in this case, the other NFs (for example, SMF, PCF, SMSF, etc.) can perform the operation suggested in the present invention. In the above description, the network function, the network entity and the network node refer to the same entity.
[0197] Figure 22 is a diagram illustrating a configuration of user equipment and a network node device according to the preferred embodiment of the present invention.
[0198] With reference to Figure 22, a UE 100 according to the present invention can include a transceiver 110, a processor 120 and a memory 130. Transceiver 110 can be configured to transmit various signals, data and information to an external device and receive various signals, data and information from the external device. The UE 100 can be connected to the external device via wire and / or wireless. The processor 120 can control the general operation of the UE 100 and can be configured to perform a function of operation processing information that will be transmitted and received from the external device. Memory 130 can store information processed by the operation for a predetermined time, and can be replaced by a buffer (not shown). Also, processor 120 can be configured to perform an UE operation suggested in the present invention.
Petition 870190101048, of 10/09/2019, p. 65/97
51/53 [0199] Referring to Figure 22, the network node device 200 according to the present invention can include a transceiver 210, a processor 220 and a memory 230. Transceiver 210 can be configured to transmit various signals, data and information to an external device and receive various signals, data and information from the external device. The network node device 200 can be connected to the external device via wire and / or wireless. Processor 220 can control the general operation of the network node device 200 and can be configured to allow the network node device 200 to perform an operation processing information function that will be transmitted and received from the external device. Memory 230 can store information processed by the operation for a predetermined time, and can be replaced by a buffer (not shown). Also, processor 220 can be configured to perform a network node operation suggested in the present invention. In detail, a UDM receives a message related to the UE server's AMF record, which includes access type information and ID (Identity) information, from a first AMF, and if there is a second AMF registered as a server AMF UE, which corresponds to the type of access information, the UDM can transmit a message related to deregistration to the second MFA.
[0200] Also, the details of the aforementioned UE 100 and the aforementioned network node device 200 can be configured in such a way that the various aforementioned embodiments of the present invention can be applied independently to the aforementioned UE 100 and the network node device 200 above, or two or more modalities can be applied simultaneously to the aforementioned UE 100 and the aforementioned network node device 200, and the repeated description will be omitted for clarification.
[0201] The previously mentioned modalities according to the present invention can be implemented by various means, for example,
Petition 870190101048, of 10/09/2019, p. 66/97
52/53 hardware, firmware, software or their combination.
[0202] If the modalities according to the present invention are implemented by hardware, the method according to the modalities of the present invention can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs) , digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable port arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.
[0203] If the modalities according to the present invention are implemented by firmware or software, the method according to the modalities of the present invention can be implemented by a type of module, procedure or function, which performs functions or operations described above. A software code can be stored in memory and can then be triggered by a processor. The memory unit can be located inside or outside the processor to transmit and receive data to and from the processor through various means that are well known.
[0204] Those skilled in the art will understand that the present invention can be realized in other specific ways than those presented in this document, without departing from the spirit and essential characteristics of the present invention. The above modalities must therefore be interpreted in all respects as illustrative and not restrictive. The scope of the invention must be determined by the appended claims and their legal equivalents, not by the description above, and any changes within the meaning and scope of equivalence of the appended claims must be covered therein. It is also apparent to those skilled in the art that claims that are not explicitly cited in the appended claims can be presented in combination as a form of the present invention or included as a
Petition 870190101048, of 10/09/2019, p. 67/97
53/53 new claim for a subsequent amendment after filing the application.
INDUSTRIAL APPLICABILITY [0205] Although the aforementioned various modalities of the present invention have been described based on the 3GPP system, the aforementioned modalities can also be applied to various mobile communication systems.

权利要求:
Claims (15)
[1]
1. Method of executing, through a Unified Data Management (UDM), a procedure related to the registration of an Access and Mobility Management Function (AMF) in a wireless communication system, CHARACTERIZED by the fact that the method comprises:
receive, through the UDM and a first AMF, a first message related to the AMF record serving a user equipment (UE), the first message comprising access type information and identity information (ID), in which the access type information indicates one of a 3rd Generation Partnership Project (3GPP) access or non-3GPP access; and based on a determination, from the type of access information and the ID information, that (i) a second MFA has been stored in the UDM as an UE serving AMF, and that (ii) the second MFA corresponds to a type of 3GPP access from the first MFA:
transmit, through the UDM and the second MFA, a second message related to deregistration.
[2]
2. Method, according to claim 1, CHARACTERIZED by the fact that it additionally comprises:
store, through the UDM in at least one computer memory, the type of access information and the ID information.
[3]
3. Method, according to claim 1, CHARACTERIZED by the fact that it additionally comprises:
receive, through the UDM and a Network Function (NF) that is an MFA, a third message related to the deletion of information related to NF from an UE context, in which the third message comprises the information of the type of access.
Petition 870190101048, of 10/09/2019, p. 94/97
2/4
[4]
4. Method, according to claim 1, CHARACTERIZED by the fact that transmitting, by the UDM to the second MFA, the second message related to the cancellation of registration comprises:
based on the cancellation of registration as a result of a subscription withdrawal, transmit the second message comprising (i) the type of access information and (ii) an indication of “Subscription Withdrawal”.
[5]
5. Method, according to claim 1, CHARACTERIZED by the fact that it additionally comprises:
based on the UDM that receives, from a Network Function (NF), a fourth message requesting information from the server AMF, in which the fourth message comprises the type of access information:
transmit, through the UDM and the NF, the server AMF information related to a type of access indicated by the type of access information.
[6]
6. Method, according to claim 1, CHARACTERIZED by the fact that it additionally comprises:
receive, through the UDM and a Network Function (NF), a request to provide UE reliability information, where the UE reachability information comprises the type of access information.
[7]
7. Method, according to claim 1, CHARACTERIZED by the fact that, based on the UE that performs a handover from a 5G (5GS) system to an Evolved Packet System (EPS), a location cancellation operation is performed by the UDM and a Local Subscriber Server (HSS) for the second AMF that corresponds to the type of 3GPP access.
[8]
8. Method, according to claim 1, CHARACTERIZED by the fact that, based on the UE that changes from a 5GS to an EPS in an idle mode, a
Petition 870190101048, of 10/09/2019, p. 95/97
3/4 location cancellation operation is performed by the UDM for the second AMF that corresponds to the type of 3GPP access.
[9]
9. Unified Data Management Device (UDM) configured to perform a procedure related to the registration of an Access and Mobility Management Function (AMF) in a wireless communication system, CHARACTERIZED by the fact that the UDM device comprises:
a transceiver;
at least one processor; and at least one computer memory operably connectable to at least one processor and storage instructions that, when executed, cause at least one processor to perform operations that comprise:
receive, by means of a first MFA, a first message related to the registration of MFA serving a user equipment (UE), the first message comprising information of the type of access and information of identity (ID), in which the information the type of access indicates one of a 3rd Generation Partnership Project (3GPP) access or non-3GPP access; and based on a determination, from the type of access information and the ID information, that (i) a second MFA was stored in the UDM apparatus as an AMF serving the UE, and that (ii) the second MFA corresponds to a type of 3GPP access from the first MFA:
transmit, to the second MFA, a second message related to deregistration.
[10]
10. UDM apparatus, according to claim 9, CHARACTERIZED by the fact that the operations additionally comprise:
Petition 870190101048, of 10/09/2019, p. 96/97
4/4
Store, on at least one computer memory, the type of access information and the ID information.
[11]
11. UDM apparatus, according to claim 9, CHARACTERIZED by the fact that the operations additionally comprise:
receive, from a Network Function (NF) that is an MFA, a third message related to the deletion of information related to NF from a UE context, in which the third message comprises the information of the type of access.
[12]
12. UDM device, according to claim 9, CHARACTERIZED by the fact that transmitting, to the second MFA, the second message related to the cancellation of registration comprises:
based on the cancellation of registration as a result of a subscription withdrawal, transmit the second message comprising (i) the type of access information and (ii) an indication of “Subscription Withdrawal”.
[13]
13. UDM apparatus, according to claim 9, CHARACTERIZED by the fact that the operations additionally comprise:
based on the reception, of a Network Function (NF), a fourth message requesting information from the AMF server, in which the fourth message comprises the type of access information:
transmit, to the NF, the AMF server information related to a type of access indicated by the information of the type of access.
[14]
14. Method, according to claim 1, CHARACTERIZED by the fact that the ID information comprises information regarding a Permanent Signature Identifier (SUPI) of the UE.
[15]
15. UDM apparatus according to claim 9, CHARACTERIZED by the fact that the ID information comprises information referring to a Permanent Signature Identifier (SUPI) of the UE.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019021178A2|2020-04-28|method of performing a procedure related to amf registration by udm in a wireless communication system, and device for the same

---

US10764951B2|2020-09-01|Registration method of user terminal in wireless communication system and apparatus therefor

---

US10205633B2|2019-02-12|Method for transmitting and receiving signal related to monitoring by SCEF in wireless communication system and apparatus for the same

---

ES2735625T3|2019-12-19|Search processing through a server that manages mobility to prevent, in the event of a search failure, the loss of downlink data stored temporarily in a service gateway

---

US10225844B2|2019-03-05|Method for selecting or reselecting relay for proximity service

---

US20190394711A1|2019-12-26|Method for receiving data related to non-3gpp via 3gpp access in wireless communication system, and apparatus for same

---

US20200245237A1|2020-07-30|Method for supporting nas signaling by base station in wireless communication system and apparatus therefor

---

EP3343963B1|2020-01-15|Method for obtaining operator network identification number of visited network

---

US10932303B2|2021-02-23|Method for transceiving signaling related to PDN connection in wireless communication system, and device therefor

---

US20170280270A1|2017-09-28|Method for controlling application related to third party server in wireless communication system and device for same

---

US20200288367A1|2020-09-10|Method for transmitting/receiving ims voice support-related signal by ng-ran in wireless communication system, and apparatus therefor

---

BR112019019001A2|2020-04-14|method to receive report, network device, method to run report, and base station

---

EP3393160B1|2020-07-08|Operation method for preventing latent erroneous operation of terminal in wireless communication system, and apparatus for same

---

US20210368576A1|2021-11-25|Signal transmission and reception method by smf in wireless communication system and device therefor

同族专利:

---

公开号 | 公开日

---

EP3618517A1|2020-03-04|

---

JP2020518203A|2020-06-18|

---

EP3618517A4|2021-01-06|

---

SG11201908702PA|2019-10-30|

---

JP6858889B2|2021-04-14|

---

US10798556B2|2020-10-06|

---

US20210029603A1|2021-01-28|

---

AU2018257151B2|2021-03-25|

---

US11096037B2|2021-08-17|

---

CA3061464A1|2019-10-24|

---

RU2728538C1|2020-07-30|

---

KR20180120609A|2018-11-06|

---

AU2018257151A1|2019-12-05|

---

US20200092710A1|2020-03-19|

---

WO2018199668A1|2018-11-01|

---

MX2019011294A|2019-12-05|

---

PH12019502405A1|2021-01-25|

---

CN110574449A|2019-12-13|

---

CL2019002700A1|2019-12-27|

---

KR102029770B1|2019-10-08|

---

US20200359194A1|2020-11-12|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

CN101064935B|2006-04-30|2010-09-29|华为技术有限公司|Method for canceling position when the mobile terminal registers two networks simultaneously|

---

ES2431051T5|2006-10-12|2018-03-06|Huawei Technologies Co., Ltd.|Method for providing a selection of access mode to a multimode terminal and corresponding system and apparatus|

---

CN102572783B|2007-05-11|2014-12-10|华为技术有限公司|Registration processing method, system and device|

---

RU2461981C2|2007-06-22|2012-09-20|Интердиджитал Текнолоджи Корпорейшн|Method and apparatus for resource management in handover operation|

---

EP2079253A1|2008-01-09|2009-07-15|Panasonic Corporation|Non-3GPP to 3GPP network handover optimizations|

---

CN101448294B|2008-01-21|2011-05-04|华为技术有限公司|Method for releasing and processing network resources and equipment thereof|

---

EP3799519A1|2008-05-09|2021-03-31|Telefonaktiebolaget LM Ericsson |Method and apparatuses for seamless handover between 3gpp and non- 3gpp networks|

---

CN110380980A|2013-02-22|2019-10-25|英特尔Ip公司|System and method for accessing network selection and flow routing|

---

WO2016072899A1|2014-11-07|2016-05-12|Telefonaktiebolaget L M Ericsson |Methods, network nodes and user equipments for improving handover in a communication network comprising a 3gpp access network and a non-3gpp access network|

---

JP6025232B1|2015-09-30|2016-11-16|日本電気株式会社|Mobile communication system, MME, communication method, and program|

---

US10142994B2|2016-04-18|2018-11-27|Electronics And Telecommunications Research Institute|Communication method and apparatus using network slicing|

---

EP3577998B1|2017-02-06|2020-11-11|Telefonaktiebolaget LM Ericsson |Control of radio technology usage by scheduling restriction|

---

EP3590278A1|2017-03-03|2020-01-08|Telefonaktiebolaget LM Ericsson |Handling service profile data for a user|

---

CN113286291A|2017-03-08|2021-08-20|华为技术有限公司|Connection processing method and device in multi-access scene|

---

US20200059989A1|2017-08-16|2020-02-20|Lenovo Pte. Ltd.|Indicating a packet data unit session as unavailable|JP6791353B2|2017-03-17|2020-11-25|日本電気株式会社|Terminal, first network device, and second network device|

---

JP2019004406A|2017-06-19|2019-01-10|シャープ株式会社|User device, amf, core network device, p-cscf and communication control method|

---

CN109392178B|2017-08-10|2021-07-13|维沃移动通信有限公司|MPDU transmission method, user side equipment and network side equipment|

---

CN109803329B|2017-11-16|2021-01-22|电信科学技术研究院|Data forwarding tunnel determination method, access and mobility management equipment and base station|

---

US10813044B2|2018-05-11|2020-10-20|Apple Inc.|Access type selection in a 5G network|

---

CN111641949A|2019-03-01|2020-09-08|华为技术有限公司|Method for updating authentication result and communication device|

---

US11228997B2|2019-06-18|2022-01-18|Mediatek Inc.|Handling of multi-access PDU session when inter-system change|

---

US11265767B2|2019-06-18|2022-03-01|Mediatek Inc.|Enhancement for multi-access PDU session|

---

WO2021025428A1|2019-08-07|2021-02-11|엘지전자 주식회사|Caller information verification based on plurality of sims|

---

WO2021089905A1|2019-11-04|2021-05-14|Nokia Technologies Oy|Dynamically unsubscribing from a plmn/npn service|

---

TWI727501B|2019-11-13|2021-05-11|財團法人資訊工業策進會|Wireless communication core network and method for analyzing mobility of user equipment in the same|

---

CN112866932A|2019-11-28|2021-05-28|中兴通讯股份有限公司|Communication connection method, device and storage medium|

---

KR20210088306A|2020-01-06|2021-07-14|삼성전자주식회사|Method and apparatus for controlling access of a ue in a non-public mobile communication network|

---

US11140618B1|2020-11-04|2021-10-05|Sprint Communications Company L.P.|Wireless data service based on geographic data network names|

法律状态:
2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762491191P| true| 2017-04-27|2017-04-27|

---

US201762501055P| true| 2017-05-03|2017-05-03|

---

PCT/KR2018/004885|WO2018199668A1|2017-04-27|2018-04-26|Method for performing amf registration-related procedure by udm in wireless communication system, and device therefor|

---